Architectural model for lte (long term evolution) epc (evolved packet core) deployment

ABSTRACT

A new deployment model enables a seamless migration to LTE (long term evolution)/EPC (Evolved packet core). In addition, an intelligent edge gateway (IEG) supports future distributed architecture and a converged network for service providers. Specifically, the model supports existing data services (e.g. UMTS) and the delivery of LTE services does not affect the existing data services. Moreover, a distributed architecture is employed, such that, local traffic is optimally routed at the edge and backhaul is minimized The system can also provide support for enhanced Femto cell 3GPP access to a home network.

RELATED APPLICATIONS

This application is a continuation of, and claims priority to each of,U.S. patent application Ser. No. 14/590,856 entitled “A NEWARCHITECTURAL MODEL FOR LTE (LONG TERM EVOLUTION) EPC (EVOLVED PACKETCORE) DEPLOYMENT,” Jan. 6, 2015, which is a continuation of U.S. patentapplication Ser. No. 14/033,050 entitled “A NEW ARCHITECTURAL MODEL FORLTE (LONG TERM EVOLUTION) EPC (EVOLVED PACKET CORE) DEPLOYMENT,” filedSep. 20, 2013 (now U.S. Pat. No. 8,964,647, issued Feb. 24, 2015), whichis a continuation of U.S. patent application Ser. No. 12/402,239entitled “A NEW ARCHITECTURAL MODEL FOR LTE (LONG TERM EVOLUTION) EPC(EVOLVED PACKET CORE) DEPLOYMENT,” filed Mar. 11, 2009 (now U.S. Pat.No. 8,565,150, issued Oct. 22, 2013). The entireties of the foregoingapplications are hereby incorporated by reference herein.

TECHNICAL FIELD

The subject disclosure relates to wireless communications and, moreparticularly, to an architectural model, which provides a phasedevolution path that enables migration to Evolved packet core (EPC)architecture and beyond.

BACKGROUND

Mobile data communications is evolving quickly because of globalcommunication networks and devices such as the Internet, intranets,laptops, PDAs (personal digital assistants) and increased requirementsof workforce mobility. Third generation mobile system (3G) technologies(e.g., UMTS-Universal Mobile Telecommunications System) are consideredenhancements to GSM (Global System for Mobile telecommunications)cellular standards.

3GPP (Third generation partnership project) standards define an EPC(evolved packet core) that supports packet-switched traffic only. One ofthe main advantages of EPC is that interfaces are based on IP protocolsand thus all services can be delivered through packet connections (e.g.,data, voice, media, etc.). Mobile operators can employ a single-packetnetwork for all services by utilizing the EPC. With the LTE (long termevolution) and EPC standards near completion, mobile operators aregearing up to deploy the new 3GPP standard architecture. Although thenew standard EPC architecture offers many advantages, there are stillmany gaps in between the new architecture and the conventional deployedsystems (e.g. 3G radio access networks). Furthermore, the migration pathhas to be carefully planned to maximize the investment yet provideseamless evolution of the mobile core network.

The core mobile data network has seen its traffic demand increasedramatically in the past few years and is expected to grow even faster.Various challenges are faced in designing a packet core network. Some ofthese challenges include, managing the evolution of the packet corewithout impact to existing data services, considering the need toseparate user plane traffic and control traffic, migration from acentralized deployed architecture to a more distributed architectureand/or migration of network intelligence to the edge. In addition,deployment of EPC systems has increased cost and management complexity.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1B illustrate high-level system diagrams depicting examplesystem architectures for an EPC (evolved packet core) in accordance withan aspect of the subject disclosure.

FIG. 2 illustrates an example network architecture for migration towardsan EPS, in accordance with an aspect of the disclosure.

FIG. 3 illustrates an example system that depicts a co-existingarchitecture (none roaming) with a combined S-GW (serving gateway) andPDN-GW (packet data network gateway) at the core, according to an aspectof the subject specification.

FIG. 4 illustrates an example hybrid architecture that can be employedfor migrating to LTE/EPC standards, according to an aspect of thespecification.

FIG. 5 illustrates an example long term evolution mobile corearchitecture that can meet the long term need of a converged network andthat supports integrated telecommunication services in accordance withan aspect to the subject system.

FIG. 6 illustrates an example high level system that depicts anintelligent edge gateway (IEG), according to an aspect of the subjectdisclosure.

FIG. 7 illustrates an example methodology that facilitates migrationtowards a LTE/EPC with minimal impact on existing services in accordancewith an aspect of the subject disclosure.

FIG. 8 illustrates an example methodology that can be employed at aninitial phase to establish LTE services during migration to EPC,according to an aspect of the subject specification.

FIG. 9 illustrates an example methodology that can optimize routing atthe edge and provide locally managed services, according to an aspect ofthe subject disclosure.

FIG. 10 illustrates an example methodology that facilitates separatingsignaling and user data path, such that, signaling elements arecentralized and user path elements are distributed at the edge.

FIG. 11 illustrates a block diagram of a computer operable to executethe disclosed migration and/or long term evolution architectures.

DETAILED DESCRIPTION

The claimed subject matter is now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the claimed subject matter. It may beevident, however, that the claimed subject matter may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the claimed subject matter.

As used in this application, the terms “component,” “module,” “system”,“interface”, or the like are generally intended to refer to acomputer-related entity, either hardware, a combination of hardware andsoftware, software, or software in execution. For example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a controller and the controller can be a component. One or morecomponents may reside within a process and/or thread of execution and acomponent may be localized on one computer and/or distributed betweentwo or more computers. As another example, an interface can include I/Ocomponents as well as associated processor, application, and/or APIcomponents.

Furthermore, the claimed subject matter may be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ),smart cards, and flash memory devices (e.g., card, stick, key drive . .. ). Additionally it should be appreciated that a carrier wave can beemployed to carry computer-readable electronic data such as those usedin transmitting and receiving electronic mail or in accessing a networksuch as the Internet or a local area network (LAN). Of course, thoseskilled in the art will recognize many modifications may be made to thisconfiguration without departing from the scope or spirit of the claimedsubject matter.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

Moreover, terms like “user equipment,” “mobile station,” “mobile,”subscriber station,” “access terminal,” “terminal,” “handset,”, andsimilar terminology, refer to a wireless device utilized by a subscriberor user of a wireless communication service to receive or convey data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream. The foregoing terms are utilized interchangeably inthe subject specification and related drawings. Likewise, the term “NodeB,” employed herein can additionally denote an “access point,” “basestation,” “evolved Node B,” “home Node B (HNB),” and the like, andrefers to a wireless network component or appliance that serves andreceives data, control, voice, video, sound, gaming, or substantiallyany data-stream or signaling-stream from a set of subscriber stations.Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,”, “operator”, “customer,”“consumer,” and the like are employed interchangeably throughout thesubject specification, unless context warrants particular distinction(s)among the terms. It should be appreciated that such terms can refer tohuman entities or automated components supported through artificialintelligence (e.g., a capacity to make inference based on complexmathematical formalisms) which can provide simulated vision, soundrecognition and so forth. In addition, the terms “wireless network” and“network” are used interchangeable in the subject application, whencontext wherein the term is utilized warrants distinction for claritypurposes such distinction is made explicit. Further, the terms “existingservices” and “existing architecture” used herein can include 2G/3Gservices and architectures respectively.

With telecommunication networks evolving in the direction of IP(Internet Protocol)-based services and traffic moving towards an all IPenvironment, the migration of network intelligence towards the “edge” ofthe networks via IP addressing capabilities is having a significantimpact on operators' ability to manage and control their networks interms of providing intelligent, integrated services. Systems and/ormethods are presented herein that can provide a phased evolution pathfor a service provider to migrate existing deployment architecture tothe new EPC (Evolved Packet Core) architecture and can provide a clearpath to solve issues associated therewith. In addition, a networkarchitecture model is provided, which is intelligently distributed yetprovides some central management capability. It can be appreciated thatthe EPC standards can be the technical specification defined by the 3rdGeneration Partnership Project's (3GPP's) Technical Specification GroupServices and System Aspects entitled “Architecture enhancements fornon-3GPP accesses, Release 8” and identified as “3GPP TS 23.402 V8.4.1(2009-01)”, which is incorporated herein by reference in its entirety.

SAE (System Architecture Evolution)/EPC is defined by 3GPP in Release 8as a new core network with a flatter all-IP architecture, that can beutilized to enable a higher-data-rate, lower-latency packet-optimizedsystem that supports multiple radio-access technologies. The SAE/EPCsupports most any services (including voice) in a packet-switcheddomain. Specifically, the SAE/EPC can support the EUTRAN (Evolved UMTSTerrestrial Radio Access Network), which utilizes an OFDMA (orthogonalfrequency division multiple access) based air interface as defined bythe 3GPP standards. Moreover, the complete packet system consisting ofthe EUTRAN and the EPC is called the Evolved Packet System (EPS). Thecombination of LTE and SAE provides an all-IP, packet only widebandOFDMA system that can improve performance by providing higher datarates, improved spectral efficiency and reduced latency.

In one aspect, the EPS architecture can include only two nodes in theuser plane, namely, a base station and a core network Gateway (GW).Typically, a node that performs control-plane functionality(MME-Mobility Management Entity) can be separated from a node thatperforms bearer-plane functionality (GW), with a well-defined openinterface between them (S11), and by using the optional interface S5 theGateway (GW) can be split into two separate nodes. Thus, throughputtraffic and control signal processing can be independently scaled. FIGS.1-4 provide an example network architecture that optimizes topologicallocations of nodes within the network in order to optimize the networkin different aspects.

The systems and methods disclosed herein, in one aspect thereof, canfacilitate realistic phased architectural evolution of a deployednetwork (e.g. 3G radio access network). The system facilitates reducedlatency and higher data performance through a flatter all-IParchitecture and provides support for both LTE radio-access networks andinterworking 3G radio-access networks. In one aspect, a PDN-GW (PacketData Network Gateway) is deployed at a core, for example, a NDC(National Data Center) and an S-GW (Serving Gateway) is deployed at anedge, for example a RDC (Regional Data Center), in a manner such thatexisting services, for example, provided by 3G radio-access networks arenot affected.

According to another aspect, a network architecture is provided whereina PDN-GW and S-GW can be deployed together at the core (e.g. NDC) duringan initial migration deployment. Moreover, deploying the S-GW at thecore can reduce costs and management complexity of the system. Further,the existing services, for example, provided by 3G radio-access networkscan be delivered with zero or minimal impact.

In accordance with another aspect, a hybrid architecture is utilized formigrating to LTE/EPC standards, wherein an edge PDN-GW and S-GW aredeployed together at an edge and a core PDN-GW is deployed at the core.Specifically, the edge PDN-GW and core PDN-GW are deployed in ahierarchical manner. The deployment provides a faster response time forreal time traffic and local management and/or routing of services at theedge.

Yet another aspect of the disclosed subject matter relates to a longterm evolution mobile core architecture that can meet the long term needof a converged network and that is inline with long term 3GPPstandardization. Specifically, the architecture is distributed, suchthat, control plane elements are less distributed and user planeelements are distributed at an edge. More specifically, an intelligentedge gateway (IEG) is deployed at the edge. In one example, the IEG canintelligently route traffic at the edge, such that response time andperformance is improved.

An additional aspect of the subject disclosure relates to a method thatfacilitates migration towards a LTE/EPC with minimal impact on existingservices. In one example, a PDN-GW can be utilized at the core and anS-GW can be utilized at the edge. In another example, a PDN-GW and anS-GW can be utilized together at the core and can provide centralizedmanagement. In yet another example, a PDN-GW can be utilized at thecore, along with, a PDN-GW and an S-GW that can be utilized together atthe edge. LTE services can be established by employing the PDN-GW(s) andS-GW, without affecting the existing (e.g. UMTS) services. Further, inone aspect, control plane elements can be less distributed and userplane elements can be distributed at the edge. Specifically, an IEG thatsupports mobility and distributed architecture can be utilized at theedge. Moreover, LTE services can be established by employing thesomewhat centralized control plane elements, distributed user planeelements and the IEG without affecting existing (e.g. UMTS) services.

Referring initially to FIGS. 1A-1B, there illustrated are high-levelsystem diagrams depicting example system architectures 100, 102 for EPCin accordance with an aspect of the subject disclosure. The systems 100,102 can provide various advantages of EPC, such as, but not limited to,reduced latency and higher data performance through a flatter all-IParchitecture and provides support for both LTE radio-access networks andinterworking with 3G radio-access networks. Moreover, the systems 100,102 can provide optimization for all services provided via IP.

FIG. 1A illustrates system 100 that can deploy a PDN-GW (Packet DataNetwork Gateway) 104 in a core 106, for example a central managementcenter, such as, but not limited to a NDC (National Data Center) withS-GW (Serving Gateway) 108 deployed at an edge 110, such as but notlimited to, a RDC (Regional Data Center). The deployment illustrated inFIG. 1A provides minimum impact on existing services (e.g. UMTSservices) and is cost effective. In addition, since the S-GW 108 isdeployed at the edge, backhaul from an eNodeB (not shown) issubstantially reduced.

As shown in FIG. 1A, the main components of EPC, for example, as definedby the 3GPP standards, include a PDN-GW 104 and S-GW 108. Typically, theS-GW 108 can terminate the interface towards EUTRAN. For each UE (userequipment) associated with the EPS, at a given point of time, a singleS-GW 108 can be employed. The S-GW 108 can be employed for routingand/or forwarding of user data packets and can operate as a localMobility Anchor point for inter-eNodeB handover. Further, the S-GW 108can perform 3GPP Anchor function that provides mobility anchoring forinter-3GPP mobility (terminating S4 and relaying the traffic between2G/3G system and PDN-GW 104). For idle state UEs associated with theS-GW 108, the S-GW 108 can terminate a DL (downlink) data path andtrigger paging when DL data arrives for the UE by utilizing downlinkpacket buffering and initiation of network triggered service requestprocedure. Furthermore, the S-GW 108 can manage and/or store UEcontexts, e.g. parameters of the IP bearer service, network internalrouting information. Additionally, the S-GW 108 can perform replicationof the user traffic in case of lawful interception.

The PDN-GW 104 is the node that terminates the SGi interface towards thePDN. If a UE is accessing multiple PDNs, there can be more than one PDNGW for that UE. The PDN-GW provides connectivity to the UE to externalpacket data networks by being the point of exit and entry of traffic forthe UE. In one aspect, the PDN-GW 104 can be employed as a mobilityanchor for mobility between 3GPP access systems and non-3GPP accesssystems, such as but not limited to, such as WiMAX and 3GPP2 (CDMA 1Xand EvDO). The PDN-GW 104 can perform policy enforcement, per-user basedpacket filtering (e.g. by deep packet inspection), charging support,lawful Interception, UE IP address allocation and/or packet screening.According to one embodiment, the PDN-GW 104 can be deployed in the core106, such that, the connectivity and/or services between the UE andexternal packet data networks are managed within a central location.

FIG. 1B, illustrates an alternate network architecture 102 wherein bothPDN-GW 104 and S-GW 108 can be deployed together at core 106 duringinitial deployment. By deploying the S-GW-108 at a central location,such as, the core 106 (as opposed to edge 110 in FIG. 1A), costs andcomplexity can be further reduced. However, a long backhaul from eNodeB(not shown) to S-GW 108 can be encountered. The deployment optionsillustrated in FIG. 1A and FIG. 1B can be modeled based on a cost andimpact analysis and synch up with an SGSN team. It can be appreciatedthat architectures 100 and 102 can deploy components defined in the EPCstandards along with currently employed components (not shown) by the 3Gradio access networks such that existing services (e.g. 3G) are notaffected.

FIG. 2 illustrates an example network architecture for migration towardsan EPS, in accordance with an aspect of the disclosure. System 200 canbe employed to deploy EPS functionality without affecting 3G servicesand/or 3G architecture. The 3G architecture can be based on the 3GPP(Third Generation Partnership Project) Release 99 specification.However, it is to be understood that the subject disclosure can beapplied to any UMTS telecommunications architecture, including by way ofexample, Release 5 (R5) and, R5 and Release 6 (R6) 3GPP standards.Further, it can be appreciated that the S-GW 108 and PDN-GW 104 caninclude functionality, as more fully described herein, for example, withregard to systems 100, 102.

Typically, a UMTS network includes three interacting domains; a userequipment (UE) domain (not shown), a UMTS Terrestrial Radio AccessNetwork (UTRAN) domain (not shown), and a core network (CN) domain, forexample, 200. The UTRAN domain is also referred to as the access networkdomain and the CN is referred to as the core network domain, the both ofwhich comprise an infrastructure domain. The Core Network can includepacket-switched elements include a serving GPRS (General packet radioservice) support node (SGSN) 202 and gateway GPRS support node(GGSN)/Policy and charging enforcement function (PCEF) 204. Some networkelements such as an EIR (equipment identity register), HLR (homelocation register), VLR (visitor location register) and AuC(authentication center) (not shown) can also be utilized.

A function of the system 200 is to provide switching, routing andtransit for user traffic. The system 200 also contains databases andnetwork management functions. The system 200 has several interfaces thatcan be configured and dimensioned. An Iu-PS (packet-switched) referencepoint interfaces an RNC (radio network controller) (not shown) of theaccess network to the SGSN entity 202 for data from/to the SGSN 202. AGn interface is provided between the SGSN 202 and the GGSN/PCEF 204.PCEF (Policy and charging enforcement function) is typically disposed inGGSN/PCEF 204 and can receive Policy and charging rules (PCR) 212 viathe Gx interface. Further, Subscriber Policy Repository (SPR) 214 can beaccess via Sp interface. The GGSN/PCEF 204 can be coupled to an offlinecharging system (OFCS) and/or online charging system (OCS) 210, throughGz and Gy interfaces respectively. A Gi Interface can be located betweenthe GGSN/PCEF 204 and an external PDN (Public Data Network). Further,the SGSN 202 can connect to an HSS (Home subscriber server) 206 via a Grinterface. The HSS 206 is a master user database that supports thenetwork entities that actually handle calls and can containsubscription-related information (user profiles), perform authenticationand authorization of a user, and provide information about the user'sphysical location.

In addition to the conventional UMTS network, system 200 can include EPScomponents, such as, an MME (Mobility management entity) 208, S-GW 108and PDN-GW 104. According to an aspect, the MME 208 and S-GW 108 can bedeployed at an edge, for example, regional data center 110 and thePDN-GW 104 can be deployed in the national data center 106. Typically,the MME 208 can manage mobility, UE (User Equipment) identities andsecurity parameters. The MME 208 can be employed for idle mode UEtracking and paging procedure including retransmissions, beareractivation and/or deactivation process and can also be responsible forchoosing the S-GW 108 for a UE at the initial attach and at time ofintra-LTE handover involving Core Network (CN) node relocation. The MME208 can interact with the HSS 206 by employing an S6a interface.Moreover, the S6a interface enables transfer of subscription andauthentication data for authenticating and/or authorizing user access tothe evolved system (AAA interface) between MME 208 and HSS 206.

The MME 208 can check the authorization of a UE and enforce UE roamingrestrictions. Further, the MME 208 can be a termination point in thenetwork 200 for ciphering/integrity protection for NAS (Non-AccessStratum) signaling and can facilitate security key management. Lawfulinterception of signaling can also be supported by the MME 208.According to an aspect, the MME 208 can provide control plane functionfor mobility between LTE and 2G/3G access networks with the S3 interfaceterminating at the MME 208 from the SGSN 202. Specifically, the S3interface enables user and bearer information exchange for inter 3GPPaccess network mobility in idle and/or active state and is based on theGTP protocol and the Gn interface as defined between SGSNs.

According to yet another aspect, the MME 208 can connect to the S-GW 108located at the edge 110 via S11 interface. The S-GW 108 can employ anS1-U interface that provides a per bearer user plane tunneling betweenthe Evolved UTRAN (not shown) and S-GW 108. The S1-U interface cancontain support for path switching during handover between eNodeBs andcan be based on the GTP-U protocol that is also used for Iu user planein the Rel-7 architecture. In one aspect, the S-GW 108 communicates withthe PDN-GW 104 in the core 106 by utilizing an S5 interface thatprovides user plane tunneling and tunnel management for the PDNconnectivity.

The SGSN 202 can interface with the PDN-GW 104 by employing a Gninterface. Further, the PDN-GW 104 employs a SGi interface to connectwith a packet data network. In an example, the packet data network canbe an operator external public or private packet data network or anintra operator packet data network, e.g. for provision of IMS services.The SGi interface corresponds to Gi and Wi interfaces and can supportmost any 3GPP or non-3GPP access. According to an aspect, the servicescontrolled by the PDN-GW 104 and/or GGSN/PCEF 204 can be centrallymanaged by utilizing the deployment in FIG. 2. In one example, thesystem 200 can be deployed as an initial architecture during migrationto a 3GPP standard architecture.

Referring now to FIG. 3, there illustrated is an example system 300 thatdepicts a co-existing architecture (none roaming) with combined S-GW 108and PDN-GW 104 at the core, according to an aspect of the subjectspecification. In particular, both PDN-GW 104 and S-GW 108 can bedeployed together at the core 106, such that, a minimum impact is madeon existing (e.g. UMTS) services. It can be appreciated that the S-GW108, PDN-GW 104, SGSN 202, GGSN/PCEF 204, HSS206, MME 208, OCS/OFCS 210,PCR 212, and SPR 214 can include functionality, as more fully describedherein, for example, with regard to systems 100, 102 and 200.

According to an aspect, deploying the S-GW 108 along with the PDN-GW 104at the core 106 can substantially reduce costs. The system 300 cansupport an existing 3G deployment model and can provide support forservice continuity. Further, system 300 can leverage policy and chargingcontrol mechanisms efficiency and can provide for a smooth built up forLTE traffic and transition. However, since S-GW 108 and PDN-GW 104 arein the core 106, latency for real time services can increase.Additionally or alternately, local traffic routing cannot be supportedat the edge 110 (e.g. RDC). It can be appreciated that the system 300can be deployed as an initial architecture during migration to a 3GPPstandard architecture.

Referring now to FIG. 4, there illustrated is an example hybridarchitecture that can be employed for migrating to LTE EPC standards,according to an aspect of the specification. It can be appreciated thatthe S-GW 108, PDN-GW 104, SGSN 202, GGSN/PCEF 204, HSS206, MME 208,OCS/OFCS 210, PCR 212, and SPR 214 can include functionality, as morefully described herein, for example, with regard to systems 100, 102,200 and 300. System 400 can be deployed as an intermediate architectureduring migration to 3GPP architecture that can provide a flexibledeployment based on mid-term business need and traffic projections.

According to an embodiment, system 400 deploys a PDN-GW 402 with S-GW108 at the edge 110 (e.g. in RDC) and a PDN-GW 104 at the core 106 (e.g.NDC) in a hierarchical manner. It can be appreciated that thefunctionality of the edge PDN-GW 402 is substantially similar to thecore PDN-GW 104 as described with respect to systems 100, 102, 200 and300. The edge and core PDN-GW 402, 104 can enable a flexible deploymentarchitecture that can support increasing LTE traffic. Moreover,simultaneous IP connections can be made to the multiple PDN-GWs (402,104) offered by the EPC and LTE traffic can be increased. Depending ontraffic projections and transition model, the split of local andcentralized traffic can change over time. As an example, for data, thesplit can start with 80% central and 20% local (opposite for voicetraffic).

The system 400 provides a shortened latency for real time traffic sincethe edge PDN-GW 402 can facilitate local management and/or routing ofservices. Further, according to an aspect, the edge PDN-GW 402 canprovide optimized traffic routing at the edge and increased support forlocal breakout at the edge. The architecture depicted in FIG. 4 canprovide flexible deployment, for example, can support overlay VoIP(Voice over IP) services. Furthermore, system 400 can provide flexiblepolicy and charging support and default bearers at the edge PDN-GW 402.

In one aspect, the edge PDN-GW 402 can be connected to the SGSN 202 by aGn interface and can employ a Gx interface to access the PCR 212.Moreover, services can create a data path from UE (to eNodeB) throughregional S-GW 108, which is tunneled to PDN-GW 104 at core 106.Accordingly, existing services through SGSN 202 are not impacted and canbe delivered as usual. Specifically, the PDN-GW 402 can facilitateoptimal local routing of traffic and/or services at the edge, thus,reduce latency and improve performance In one example, the deployment ofsystem 400 can be flexible and can be scaled based on traffic. Theadditional PDN-GW 402 increases management complexity and/or costs,however can improve performance and reduce latency without affectingexisting services. Further, the additional PDN-GW 402 can increasebackhaul requirements and can employ intelligence to split traffics(e.g. edge policy functions).

FIG. 5 illustrates an example long term evolution mobile corearchitecture that can meet the long term need of a converged networkthat supports integrated telecommunication services in accordance withan aspect to the subject system. System 500 provides a distributedarchitecture that can facilitate routing of traffic and/or services atthe edge. It can be appreciated that the S-GW 108, SGSN 202, HSS 206,MME 208, OCS/OFCS 210, PCR 212, and SPR 214 can include functionality,as more fully described herein, for example, with regard to systems 100,102, 200, 300 and 400.

Typically, the EPS architecture, as defined by standards set by 3GPP,can include two nodes in the user plane, a base station and a corenetwork gateway (GW). An MME 208 node that performs control-planefunctionality can be employed and can be separated from a node thatperforms bearer-plane functionality (e.g. S-GW 108), with a well definedopen interface between them (S11). Further, an S5 interface can beutilized can be to split the Gateway (GW) into two separate nodes (e.g.S-GW 108 and IEG 502) to enable independent scaling and growth ofthroughput traffic and control signal processing. According to anembodiment, system 500 employs a distributed architecture, such that,databases (e.g., HSS 206, PCR 212, SPR 214, etc.) are deployed in thecore 106 and all gateways (e.g. SGSN 202, S-GW 108, IEG 502, etc) aredeployed at edge 110.

System 500 can employ an intelligent edge gateway (IEG) 502 at the edge110 (e.g. RDC) that can adhere to the 3GPP standards. Specifically,control plane elements can be centralized (e.g. at core 106) and userplane elements can be distributed at an edge 110. Additionally, userplane elements can be policy enabled and an integrated access gateway(e.g. IEG 502) can be utilized. According to an embodiment, the IEG 502can interface with the SGSN 202 over a Gn interface. Further, the IEG502 can access databases in the core 106 (e.g. NDC), such as, but notlimited to, the PCR 212 via the Gx interface and can be coupled to theOFCS and/or OCS 210 at the core 106, through Gz and Gy interfacesrespectively.

The IEG 502 can be composite edge gateway that is policy enabled and canbe deployed in a very flexible fashion that can support a convergednetwork architecture. In one aspect, the IEG 502 can intelligently routetraffic at the edge, such that backhaul to the core 106 is avoided,latency is reduced and performance is improved. System 500 illustrates atruly distributed architecture that can be inline with long term 3GPPstandardization wherein the IEG 502 can perform optimized routing at theedge 110. Moreover, system 500 can provide enhanced support for localbreakout and can allow traffic to be kept local at the edge and thusprovide shortened latency. Further, the distributed architecture ofsystem 500 can separate signaling and user data path, with centralizedsignaling elements and distributed user path elements. Specifically, thesystem 500 supports existing data services (e.g. UMTS services) and doesnot have a negative affect the existing data services. In one example,the system 500 can support enhanced Femto cell 3GPP access to a homenetwork (not shown). In one example, various AI (artificialintelligence)-based schemes can be employed for carrying out variousaspects, for example, local traffic routing can be facilitated via anautomatic classifier system and process. A classifier is a function thatmaps an input attribute vector, x=(x1, x2, x3, x4, xn), to a confidencethat the input belongs to a class, that is, f(x)=confidence(class). Suchclassification can employ a probabilistic and/or statistical-basedanalysis (e.g. factoring into the analysis utilities and costs) toprognose or infer an action that a user desires to be automaticallyperformed. A support vector machine (SVM) is an example of a classifierthat can be employed. Other directed and undirected model classificationapproaches include, e.g., naïve Bayes, Bayesian networks, decisiontrees, neural networks, fuzzy logic models, and probabilisticclassification models providing different patterns of independence canbe employed. Classification as used herein also is inclusive ofstatistical regression that is utilized to develop models of priority.

As will be readily appreciated from the subject specification, thesubject disclosure can employ classifiers that are explicitly trained(e.g. via a generic training data) as well as implicitly trained (e.g.via observing user behavior, receiving extrinsic information). Forexample, SVM's are configured via a learning or training phase within aclassifier constructor and feature selection module. Thus, theclassifier(s) can be used to automatically learn and perform a number offunctions, including but not limited to determining according to apredetermined criteria routing of data traffic at the edge.

Referring now to FIG. 6, there illustrated is an example high levelsystem 600 that depicts an intelligent edge gateway IEG 502, accordingto an aspect of the subject disclosure. In one aspect, the IEG 502 canbe an evolved data gateway that is a composite of edge functions thatsupport mobility and distributed architecture (e.g. system 500), whichcan be supported in a converged network. Further, the IEG 502 can bepolicy enabled and can be deployed in a flexible fashion that cansupport a converged network architecture. The IEG 502 can facilitateintelligent routing of local traffic and thus reduce latency. Inaddition, the IEG 502 can be deployed at the edge and optimize routingat the edge and provide increased support for local breakout.

According to an aspect, the IEG 502 can be deployed at the edge (e.g.RDC) and can include a GGSN component 602 that can facilitateinterworking between a GPRS network and the external packet switchednetwork. As an example, the IEG 502 can employ the GGSN component 602 toroute data from a packet switched network to the SGSN serving a mobileuser, and route mobile-originated packets from the SGSN to the packetswitched network. Additionally, the GGSN component 602 can keep a recordof active mobile users and an SGSN that the mobile users are attachedto, and can allocate IP addresses to mobile users. Further, GGSNcomponent 602 can also facilitate billing. It can be appreciated thatthe GGSN component 602 can include functionality provided by a GGSN(2G/3G).

The IEG 502 can also include a PCEF component 604 that can handle mostany PEP (Policy Enforcement Point) functions. Further, an S-GW 608 and aPDN-GW with LMA (local mobility anchor) 610 can also be included withinthe IEG 502. It can be appreciated that the S-GW 608 can besubstantially similar to S-GW 108 in FIG. 4 and can includefunctionality thereof. Similarly, PDN-GW with LMA 610 can besubstantially similar to PDN-GW 402 in FIG. 4 and include functionalitythereof. Additionally, PDN-GW with LMA 610 can maintain a collection ofhost routes and associated forwarding information for mobile nodeswithin a localized mobility management domain under its control.Specifically, the PDN-GW with LMA 610 can employ a protocol to manage IPnode mobility within the localized mobility management domain. Routingof mobile node data traffic can be anchored at the PDN-GW with LMA 610as the mobile node moves around within the localized mobility managementdomain.

Additionally, an ePDG component 612 can also be included in the IEG 502.According to an aspect, the ePDG component 612 can include functionalityof a PDG (packet data gateway) according to 3GPP TS 23.234 thatspecifies inter-working between 3GPP systems and WLAN. Moreover, ePDGcomponent 612 can authenticate the users and control the traffic foruntrusted network access. In particular, the ePDG component 612 canprovide functionality to deliver voice and data services over theuntrusted Internet and WiFi networks to femtocells and dual-modehandsets.

An Access SBC (session border controller) component 614 can be employedthat provides with support for delivering real-time interactive IP-basedvoice, video and multimedia sessions in critical areas, such as, but notlimited to, security, service reach maximization, SLA assurance, revenueand cost optimization, and regulatory compliance. The Access SBCcomponent 614 can satisfy requirements at a border where subscribersaccess the IMS (IP Multimedia Subsystem) core. Further, a Proxy-CallSession Control Function (P-CSCF) component 616 can be utilized as a SIP(Session Initiation Protocol) signaling contact point, theoutbound/inbound “proxy,” for subscribers within IMS as defined by 3GPP.Typically, the P-CSCF component 616 can facilitate forwarding SIPregistration messages from the subscriber's endpoint, the User Equipment(UE), in a visited network to the Interrogating-CSCF (I-CSCF) andsubsequent call set-up requests and responses to the Serving-CSCF(S-CSCF). Further, the P-CSCF component 616 can maintain the mappingbetween logical subscriber SIP URI (uniform resource identifier) addressand physical UE IP address and a security association, for bothauthentication and confidentiality, with the UE using IPsec for example.Furthermore, emergency call (E911) local routing within the visitednetwork, accounting, session timers and admission control can also besupported by the P-CSCF component 616.

FIGS. 7-10 illustrate methodologies and/or flow diagrams in accordancewith the disclosed subject matter. For simplicity of explanation, themethodologies are depicted and described as a series of acts. It is tobe understood and appreciated that the subject disclosure is not limitedby the acts illustrated and/or by the order of acts, for example actscan occur in various orders and/or concurrently, and with other acts notpresented and described herein. Furthermore, not all illustrated actsmay be required to implement the methodologies in accordance with thedisclosed subject matter. In addition, those skilled in the art willunderstand and appreciate that the methodologies could alternatively berepresented as a series of interrelated states via a state diagram orevents. Additionally, it should be further appreciated that themethodologies disclosed hereinafter and throughout this specificationare capable of being stored on an article of manufacture to facilitatetransporting and transferring such methodologies to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media.

Referring now to FIG. 7, there illustrated is an example methodology 700that facilitates migration towards a LTE/EPC with minimal impact onexisting (2G/3G) services in accordance with an aspect of the subjectdisclosure. At 702, a PDN-GW can be utilized at the core, e.g. NDC andprovide centralized management. At 704, an S-GW can be utilized at theedge, e.g. RDC and provide local management at the edge. Further, at706, LTE services can be established by employing the PDN-GW and S-GW,without affecting the existing (e.g. UMTS) services.

FIG. 8 illustrates an example methodology 800 that can be employed at aninitial phase to establish LTE services during migration to EPC,according to an aspect of the subject specification. At 802, a PDN-GWand an S-GW can be utilized together at the core and can providecentralized management. At 804, LTE services can be established and/ordelivered by employing the PDN-GW and S-GW, without affecting theexisting (e.g. UMTS) services.

FIG. 9 illustrates an example methodology 900 that can optimize routingat the edge and provide locally managed services, according to an aspectof the subject disclosure. At 902, a PDN-GW can be utilized at the core,e.g. NDC, and provide centrally managed services. At 904, a PDN-GW andan S-GW can be utilized together at the edge, for example, RDC and canprovide locally managed services. In one example, the core PDN-GW andedge PDN-GW can be utilized in a hierarchical manner. The edge PDN-GWcan facilitate local traffic routing and minimize backhaul to the core.At 906, LTE services can be established and/or delivered by employingthe PDN-GWs and S-GW, without affecting the existing (e.g. UMTS)services.

Referring to FIG. 10, there illustrated is an example methodology 1000that facilitates separating signaling and user data path, such that,signaling elements are centralized and user path elements aredistributed at the edge. At 1002, centralized control plane elements canbe utilized, for example databases, such as, but not limited to HSS,PCR, OCS/OFCS, etc. At 1004, distributed user plane elements areutilized including an IEG. Moreover, the IEG is composite of edgefunctions, which can be supported in a converged network, that supportmobility and distributed architecture. At 1006, LTE services can beestablished and/or delivered by employing the centralized control planeelements and the IEG without affecting existing (e.g. UMTS) services.

Referring now to FIG. 11, there is illustrated a block diagram of acomputer operable to execute the disclosed architectures. In order toprovide additional context for various aspects of the subjectspecification, FIG. 11 and the following discussion are intended toprovide a brief, general description of a suitable computing environment1100 in which the various aspects of the specification can beimplemented. While the specification has been described above in thegeneral context of computer-executable instructions that may run on oneor more computers, those skilled in the art will recognize that thespecification also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the specification may also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer-readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disk (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

With reference again to FIG. 11, the example environment 1100 forimplementing various aspects of the specification includes a computer1102, the computer 1102 including a processing unit 1104, a systemmemory 1106 and a system bus 1108. The system bus 1108 couples systemcomponents including, but not limited to, the system memory 1106 to theprocessing unit 1104. The processing unit 1104 can be any of variouscommercially available processors. Dual microprocessors and othermulti-processor architectures may also be employed as the processingunit 1104.

The system bus 1108 can be any of several types of bus structure thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1106includes read-only memory (ROM) 1110 and random access memory (RAM)1112. A basic input/output system (BIOS) is stored in a non-volatilememory 1110 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1102, such as during start-up. The RAM 1112 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1102 further includes an internal hard disk drive (HDD)1114 (e.g., EIDE, SATA), which internal hard disk drive 1114 may also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1116, (e.g., to read from or write to aremovable diskette 1118) and an optical disk drive 1120, (e.g., readinga CD-ROM disk 1122 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1114, magnetic diskdrive 1116 and optical disk drive 1120 can be connected to the systembus 1108 by a hard disk drive interface 1124, a magnetic disk driveinterface 1126 and an optical drive interface 1128, respectively. Theinterface 1124 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject specification.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1102, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, may also be used in the example operating environment, andfurther, that any such media may contain computer-executableinstructions for performing the methods of the specification.

A number of program modules can be stored in the drives and RAM 1112,including an operating system 1130, one or more application programs1132, other program modules 1134 and program data 1136. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1112. It is appreciated that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1102 throughone or more wired/wireless input devices, e.g., a keyboard 1138 and apointing device, such as a mouse 1140. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1104 through an input deviceinterface 1142 that is coupled to the system bus 1108, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1144 or other type of display device is also connected to thesystem bus 1108 via an interface, such as a video adapter 1146. Inaddition to the monitor 1144, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1102 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1148. The remotecomputer(s) 1148 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1102, although, for purposes of brevity, only a memory/storage device1150 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1152 and/orlarger networks, e.g., a wide area network (WAN) 1154. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich may connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1102 isconnected to the local network 1152 through a wired and/or wirelesscommunication network interface or adapter 1156. The adapter 1156 mayfacilitate wired or wireless communication to the LAN 1152, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1156.

When used in a WAN networking environment, the computer 1102 can includea modem 1158, or is connected to a communications server on the WAN1154, or has other means for establishing communications over the WAN1154, such as by way of the Internet. The modem 1158, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1108 via the serial port interface 1142. In a networkedenvironment, program modules depicted relative to the computer 1102, orportions thereof, can be stored in the remote memory/storage device1150. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

The computer 1102 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, atan 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, orwith products that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic 10BaseT wiredEthernet networks used in many offices.

It is to be noted that aspects, features, or advantages of the subjectdisclosure described in the subject specification can be exploited insubstantially any wireless communication technology. For instance, 4G,Enhanced GPRS, 3GPP LTE, 3GPP2 UMB, 3GPP UMTS, HSPA, or Zigbee.Additionally, substantially all aspects of the subject disclosure asdisclosed in the subject specification can be exploited in legacytelecommunication technologies.

What has been described above includes examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Accordingly, the presentspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “includes” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receivingdata from a network device of a first communication network; based onfirst percentage data associated with transition model data indicativeof a transition model, determining a first portion of the data that isto be directed to a first network device of a second communicationnetwork; based on second percentage data associated with the transitionmodel data, determining a second portion of the data that is to bedirected to a second network device of the second communication network;and in response to determining that a criterion associated with adefined time period has been satisfied, updating the first percentagedata to facilitate a first adjustment in the first portion of the data,and updating the second percentage data to facilitate a secondadjustment in the second portion of the data.
 2. The system of claim 1,wherein the determining the first portion of the data comprisesdetermining the first percentage data based on time-dependent trafficprojection data for the second communication network.
 3. The system ofclaim 1, wherein the updating the first percentage data comprisesupdating the first percentage data to facilitate a reduction in thefirst portion of the data, and the updating the second percentage datacomprises updating the second percentage data to facilitate an increasein the second portion of the data.
 4. The system of claim 1, wherein thedetermining the first portion of the data comprises determining thefirst portion of the data based on traffic data for the secondcommunication network.
 5. The system of claim 1, wherein the determiningthe second portion of the data comprises determining voice over Internetprotocol data.
 6. The system of claim 1, wherein the determining thatthe criterion associated with the defined time period has been satisfiedcomprises determining that the defined time period has expired.
 7. Thesystem of claim 1, wherein the operations further comprise transmittingthe first portion of the data to the first network device in accordancewith the first percentage data and transmitting the second portion ofthe data to the second network device in accordance with the secondpercentage data.
 8. The system of claim 1, wherein the operationsfurther comprise transmitting the first portion of the data to the firstnetwork device in response to receiving authentication data from a datastore of the second communication network.
 9. A method, comprising:receiving, by a device comprising a processor, communication data; basedon first percentage data associated with transition model dataindicative of a transition model, selecting, by the device, a firstportion of the communication data that is to be transmitted via a firstgateway device of a hierarchically defined communication network; basedon second percentage data associated with the transition model data,selecting, by the device, a second portion of the communication datathat is to be transmitted via a second gateway device of thehierarchically defined communication network; in response to determiningthat an expiration criterion has been satisfied, decreasing, by thedevice, the first portion of the communication data; and in response tothe determining that the expiration criterion has been satisfied,increasing, by the device, the second portion of the communication data.10. The method of claim 9, wherein the selecting the first portion ofthe communication data comprises selecting the first portion of thecommunication data based on time-dependent traffic projection data forthe hierarchically defined communication network.
 11. The method ofclaim 9, wherein the selecting the first portion of the communicationdata comprises selecting the first portion of the communication databased on policy data indicative of a policy associated with thehierarchically defined communication network.
 12. The method of claim 9,wherein the selecting the first portion of the communication datacomprises selecting the first portion of the communication data based ontraffic data indicative of an amount of data traffic for thehierarchically defined communication network.
 13. The method of claim 9,wherein the selecting the second portion of the communication datacomprises selecting voice over Internet protocol data from thecommunication data.
 14. The method of claim 9, wherein the determiningthat the expiration criterion has been satisfied comprises determiningthat a defined time period has expired.
 15. The method of claim 9,further comprising transmitting, by the device, the first portion of thecommunication data via the first gateway device in accordance with thefirst percentage data and transmitting, by the device, the secondportion of the communication data via the second gateway device inaccordance with the second percentage data.
 16. The method of claim 9,further comprising transmitting, by the device, the first portion of thecommunication data via the first gateway device in response to receivingauthentication data from a data store of the hierarchically definedcommunication network.
 17. A machine-readable storage medium comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: receiving communication data froma network device of a first communication network; in accordance with afirst fractional value associated with transition model data indicativeof a transition model, selecting a first portion of the communicationdata to be directed to a first network device of a second communicationnetwork; in accordance with a second fractional value associated withthe transition model data, selecting a second portion of thecommunication data to be directed to a second network device of thesecond communication network; and in response to determining that acriterion associated with a defined interval of time has been satisfied,updating the first fractional value to facilitate a first adjustment inthe first portion of the communication data, and updating the secondfractional value to facilitate a second adjustment in the second portionof the communication data that is different than the first adjustment.18. The machine-readable storage medium of claim 17, wherein theselecting the first portion of the communication data comprisesdetermining the first fractional value based on time-dependent trafficprojection data for the second communication network.
 19. Themachine-readable storage medium of claim 17, wherein the updating thefirst factional value comprises updating the first fractional value tofacilitate a decrease in the first portion of the communication data,and the updating the second fractional value comprises updating thesecond fractional value to facilitate an increase in the second portionof the communication data.
 20. The machine-readable storage medium ofclaim 17, wherein the operations further comprise transmitting the firstportion of the communication data to the first network device inaccordance with the first fractional value and transmitting the secondportion of the communication data to the second network device inaccordance with the second fractional value.